<?php
/**
 * <https://y.st./>
 * Copyright © 2019 Alex Yst <mailto:copyright@y.st>
 * 
 * This program is free software: you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by
 * the Free Software Foundation, either version 3 of the License, or
 * (at your option) any later version.
 * 
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
 * GNU General Public License for more details.
 * 
 * You should have received a copy of the GNU General Public License
 * along with this program. If not, see <https://www.gnu.org./licenses/>.
**/

$xhtml = array(
	'<{title}>' => 'What did you expect? Sand is the worst element.',
	'takedown' => '2017-11-01',
	'<{body}>' => <<<END
<img src="/img/CC_BY-SA_4.0/y.st./weblog/2019/06/23.jpg" alt="Tiles" class="framed-centred-image" width="800" height="480"/>
<section id="diet">
	<h2>Dietary intake</h2>
	<p>
		I dreamed I was still on speaking terms with Summer, and it was my Birthday.
		She&apos;d gone back to trying to cram birthdays down my throat.
		This time, she gave me stuff that she&apos;s apparently already given me on my fifteenth birthday, though one of the things was a giant, cloth book.
		The numbers didn&apos;t add up, but I didn&apos;t notice until I was awake; you don&apos;t give fifteen-year-olds giant cloth books.
		The other thing was a small, wooden shelf painted white with my birth name on it.
		She thought that seeing things from my past might get me to come around and accept birthday gifts.
		Instead, seeing the birth name I&apos;ve always hated tied back to me on an item I used to own sent me into mild convulsions.
		She didn&apos;t notice, but I was in a great deal of emotional pain.
		Typical of her; she doesn&apos;t notice the pain of others, and only focuses on doing whatever it is that <strong>*she*</strong> wants at the moment.
	</p>
</section>
<section id="diet">
	<h2>Dietary intake</h2>
	<p>
		For breakfast, I had 54 grams of cereal and 127 grams of soy milk.
		For lunch, I had potato gnocchi with sliced veggie dogs and cashew sauce totalling 643 grams.
		For dinner, I had 779 grams of the same.
	</p>
	<p>
		I think I got the sauce nearly right this time.
		It was a bit too runny, but the flavour was perfect.
	</p>
</section>
<section id="drudgery">
	<h2>Drudgery</h2>
	<p>
		My discussion posts for the day:
	</p>
	<blockquote>
		<p>
			The Unit 1 assignment tells us that while it&apos;s ungraded, we should still complete and submit it.
			However, it seems to lack any instructions as to what to actually do or what to submit.
			We&apos;re given code, then walked through the code with explanations as to what each part does.
			But what code do we write?
			What code do we submit?
			What are we even doing?
			Did I just miss something?
		</p>
	</blockquote>
	<blockquote>
		<p>
			Like you said, use experience deals with how the user feels when they use your website, application, or other interface.
			Usability <strong>*severely*</strong> impacts how the user feels.
			For that reason, I have to strongly disagree that user experience has to be kept separate from usability.
			The two are so entwined that they cannot be separated.
			I mean, we can talk about usability separately from user experience, but we cannot adequately and fully talk about user experience without covering usability as well.
		</p>
		<p>
			You also mention that people are using different devices and operating systems.
			It&apos;s also important to note that different users have different needs.
			For that reason, accessibility plays a major role in user experience.
			If your application doesn&apos;t have options for blind people so they don&apos;t have to do things visually, blind people aren&apos;t going to find your application usable, and thus won&apos;t have a good user experience.
		</p>
	</blockquote>
</section>
<section id="Minetest">
	<h2>Minetest</h2>
	<img src="/img/CC_BY-SA_3.0/minetest.net./weblog/2019/06/23.png" alt="Sandstone recipe" class="framed-centred-image" width="1024" height="600"/>
	<p>
		I&apos;ve completed all the recipes needed by the terra block in 0.4.0, and I&apos;ve tested them all with the exception of the cat block recipe.
		To test that, I&apos;d need nine rainbows, and those can&apos;t feasibly be acquired.
		Everything else seems to be in working order though.
		With the recipes used by the terra block defined, the next steps are to actually make the terra block function and to define the recipes used to create the terra block itself.
	</p>
	<p>
		Instead of working on that though, I took a break and worked on my new sand-inspired node.
		I didn&apos;t think I&apos;d have one, but it actually will turn out to be useful for certain other elements later.
		The premise of the node is that you compress as much of the element as you can, an it forms a node.
		If it&apos;s possible to get the node that drops the element into your inventory, you instead compress as much as you can of that.
		In the case of sand, that&apos;s the same thing, as compressing as much sand as possible means first compressing it into sandstone, then crafting nine sandstone together to compress it further.
		Then, when you dig the node, if it was crafted from nodes that drop the element, it&apos;ll then drop the full amount of the element that the uncompressed nodes would drop, which in every case so far is nine.
		Except the sand-based one, which drops nothing.
		Because sand is the worst element.
		However, you do get credit for nine sand drops.
		The logic behind this is simple.
		Each sand drop destroys three sand.
		The compressed sand node contains thirty-six sand.
		You lose it all, but you get the maximum amount of points, where if you&apos;d done this by individually dug sandstone nodes, crafted the dropped sand into more sandstone, and repeated the process, you&apos;d be left with three sand that couldn&apos;t be crafted into sandstone until you found a fourth sand.
		Then with the four sand, you&apos;d make a sandstone and get back one sand.
		You always need that one extra sand in order to destroy three and get one point.
		This skips that, though you need exactly thirty-six sand to do it.
	</p>
	<p>
		I&apos;d thought that this node would be especially helpful for string, flint, and blueberries, none of which can be actually crafted into usable nodes.
		Now that I think on it though, it doesn&apos;t provide a way to do that with flint, as flint comes from gravel, so you&apos;d craft nine gravel together.
		Building out of flint still isn&apos;t possible yet.
	</p>
</section>
END
);
